Mobile application security assessment

ABSTRACT

The security of mobile applications may be assessed and used to enhance the security of mobile devices. In one example, a method may include determining security scores of one or more mobile applications, the security scores defining a level of security risk corresponding to the one or more mobile applications. The method may further include receiving a policy relating to mobile applications that are permitted to be used by the mobile device, the policy including a threshold security score value; and receiving the requested security scores. The method may further include restricting use of selected ones of the one or more mobile applications when a security score corresponding to the one or more mobile applications is below the threshold security score value.

BACKGROUND

Mobile applications, also called mobile apps, are software applications,usually designed to run on smart phones and tablet computers. Mobileapplications are commonly available through application distributionplatforms, which are often operated by the owner of the mobile operatingsystem, a telecommunication carrier, the device manufacturer, businessenterprises, or industry consortiums (e.g. Android Developer Groups).Developers may create mobile applications and upload the mobileapplications to the application distribution platform. Users may browsethe mobile applications and download desired mobile applications tosmart phones, tablet computers, and/or any device with a compatibleoperating system capable of running the application on behalf of theusers.

The amount of review and/or quality checks relating to mobileapplications, available to an application distribution platform, mayvary based on the application distribution platform. For someapplication distribution platforms, user feedback relating to mobileapplications may be the primary method through which users browsing themobile applications judge the quality of the mobile application.Feedback ratings, from a typical user, may be primarily directed to thefeatures provided by the mobile application and the user interfacepresented by the mobile application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 2 is a diagram of example components of a device that maycorrespond to one or more of the devices shown in FIG. 1;

FIG. 3 is a diagram of operations relating to the application scoreserver shown in FIG. 1;

FIG. 4 is a diagram of example operations relating to the modificationof security scores, for mobile applications, based on an in-depthanalysis of a mobile application;

FIG. 5 is diagram illustrating an example of a security review processto obtain a security score for a mobile application;

FIG. 6 is a flow chart illustrating an example process relating to asentinel application;

FIG. 7 is a diagram illustrating an example user interface that may bepresented by the sentinel application;

FIG. 8 is a flow chart illustrating an example process relating toanother implementation of the sentinel application; and

FIG. 9 is a diagram illustrating an example of the operation of anapplication policy server shown in FIG. 1.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

Techniques described herein may provide for systems and/or methods thatassess the security or other attributes (for example reliability) ofmobile applications.

Security assessment may be implemented based on an initial securityscore that is obtained for mobile applications. The security score maybe augmented based on additional automated and/or manual analysis of thebinary or source code and/or observed behavior of the mobileapplication. For example, all mobile applications may be assigned abasic security score. Developers may choose to submit a mobileapplication for a more comprehensive security analysis based on thebinary or source code and/or observed behavior of the mobileapplication. A mobile application that undergoes the more comprehensivesecurity analysis may be eligible for an increased security score.

The mobile application security scores may be used in a number of ways.In one implementation, a user may be able to view the security score ofa mobile application that the user is considering installing.Alternatively or additionally, a user may be provided with a list of allthe mobile applications that are installed on the user's mobile deviceand a corresponding list of security scores. In this way, a user mayperform a self audit relating to the security of the installed mobileapplications.

In some implementations, corporations or other entities that deploy anumber of mobile devices, such as mobile devices given to employees ofthe corporation, may create policies, for the mobile devices, based onthe security scores. For example, certain employees, such as thoseemployees that deal with sensitive company information, may only beallowed to install mobile applications that have at least a firstthreshold value security score. Other employees may only be allowed toinstall mobile applications that have at least a second threshold value,lower than the first threshold value, security score.

The term security, as used herein in the context of mobile applicationsinstalled on mobile devices, may relate to the trustworthiness of themobile application to intentionally or unintentionally create securityrisks for the mobile device. The term “security” may be broadly definedas any characteristic, attribute, function, etc. of a mobile applicationwhich is being assessed to determine if the application causes harm orthe risk of harm to the mobile device, causes harm or the risk of harmto any device to which the mobile device is connected, or causes harm,risk of harm or any other negative effect to the user of the mobileapplication. A security risk may broadly be defined as a risk that themobile device, without explicit or implied user permission, will monitoruser actions, provide data of the user or the mobile device to anotherentity, and/or enable a malicious application or service to monitorand/or obtain data relating to the user or the mobile device.

FIG. 1 is a diagram of an example environment 100 in which systemsand/or methods described herein may be implemented. As illustrated,environment 100 may include a network 110 that connects a number ofdevices and/or systems. The devices and/or systems may include mobiledevices 120 and servers 140, 150, and 160.

Network 110 may include one or more networks of any type, such as alocal area network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network, such as the Public SwitchedTelephone Network (PSTN) or a Public Land Mobile Network (PLMN), anintranet, the Internet, or a combination of networks. Network 110 mayinclude one or more wireless portions that provide wireless connectivityto mobile devices 120. Alternatively or additionally, network 110 mayprovide a wired connection to mobile devices 120.

Mobile devices 120 may include portable computing and communicationdevices, such as a personal digital assistant (PDA), a smart phone, acellular phone, a laptop computer with connectivity to a wirelessnetwork, a tablet computer, etc. Mobile devices 120 may connect, throughnetwork 110, to one or more of servers 140, 150, and 160. Althoughdevices 120 will generally be described as mobile devices herein, insome implementations, devices 120 may include fixed devices, such asdesktop computers, media centers, or other computing devices that arenot designed for portability.

Each of mobile devices 120 may include one or more mobile applicationsthat are installed on the mobile device. One mobile application that maybe particularly installed on mobile devices 120 includes a sentinelapplication 130, which may include a mobile application that providesinformation relating to the security scores of other mobile applicationsthat are installed on a mobile device 120. Sentinel application 130 maybe installed as a background service. In some implementations, sentinelapplication 130 may inform the user, of mobile device 120, of thesecurity scores of mobile applications that are being browsed, at mobileapplication server 140, or that are about to be installed on mobiledevice 120. In other implementations, sentinel application 130 mayprovide additional functionality, such as filtering or blocking mobileapplications that have insufficient security scores. Sentinelapplication 130 will be described in more detail below with reference toFIGS. 6-9.

Environment 100 may additionally include servers 140, 150, and 160.These servers may include mobile application servers 140, an applicationscore server 150, and an application policy server 160.

Mobile application servers 140 may include web servers, applicationservers, or other types of servers that provide an applicationdistribution platform for mobile applications that are to be installedand/or executed by mobile devices 120. For example, a mobile applicationserver 140 may provide an online application store in which users ofmobile devices 120 can browse and install mobile applications. Mobileapplication server 140 may also allow users to provide feedback relatingto the quality of mobile applications that the users have downloaded.

Application score server 150 may include web servers, applicationservers, or other types of servers that generate, maintain, and displaysecurity scores relating to the security of mobile applications. Thesecurity scores may include scores that are automatically generated frompublicly available mobile application data. The automatically generatedsecurity scores may be additionally augmented based on an automatedand/or manual analysis of the code corresponding to the mobileapplication. The operation of application score server 150 will bedescribed in more detail below with reference to FIGS. 3-5.

Application policy server 160 may include web servers, applicationservers, or other types of servers that allow corporations or otherentities to implement policies for one or more mobile devices 120. Forexample, each mobile device 120, that is controlled by a particularentity, may be assigned a policy that restricts certain mobileapplications from being downloaded, installed, or executed. The policymay be based on security scores provided by application score server150. Application policy server 160 will be described in more detailbelow with reference to FIGS. 8 and 9.

One network 110, three mobile devices 120, two mobile applicationservers 140, one application score server 150, and one applicationpolicy server 160 are illustrated in FIG. 1 for simplicity. In practice,there may be additional or fewer networks 110, mobile devices 120,mobile application servers 140, application score servers 150, and/orapplication policy servers 160. Mobile application servers 140 andapplication score server 150, although shown as a single component inFIG. 1, may, in practice, be implemented as one or more computingdevices that may potentially be geographically distributed.

Although FIG. 1 shows example components of environment 100, in otherimplementations, environment 100 may contain fewer components, differentcomponents, differently arranged components, or additional componentsthan those depicted in FIG. 1. Alternatively, or additionally, one ormore components of environment 100 may perform one or more tasksdescribed as being performed by one or more other components ofenvironment 100.

FIG. 2 is a diagram of example components of a device 200 that maycorrespond to one or more devices of environment 100, such as one ofmobile devices 120, mobile application servers 140, application scoreserver 150, or application policy server 160. As illustrated in FIG. 2,device 200 may include a bus 210, a processing unit 220, a memory 230,an input device 240, an output device 250, and a communication interface260.

Bus 210 may permit communication among the components of device 200.Processing unit 220 may include one or more processors ormicroprocessors that interpret and execute instructions. In otherimplementations, processing unit 220 may be implemented as or includeone or more Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), or the like.

Memory 230 may include a random access memory (RAM) or another type ofdynamic storage device that stores information and instructions forexecution by processing unit 220, a read-only memory (ROM) or anothertype of static storage device that stores static information andinstructions for the processing unit 220, and/or some other type ofmagnetic or optical recording medium and its corresponding drive forstoring information and/or instructions.

Input device 240 may include a device that permits an operator to inputinformation to device 200, such as a keyboard, a keypad, a mouse, a pen,a microphone, a touchscreen display, one or more biometric mechanisms,and the like. When device 200 includes one of mobile devices 120, inputdevice 240 may particularly include a touchscreen display or a keyboardor keypad designed for mobile devices 120. Output device 250 may includea device that outputs information to the operator, such as a display, aspeaker, etc.

Communication interface 260 may include any transceiver-like mechanismthat enables device 200 to communicate with other devices and/orsystems. For example, communication interface 260 may include mechanismsfor communicating with other devices, such as other devices associatedwith environment 100. When device 200 includes one of mobile devices120, communication interface 260 may include antennas and othercircuitry associated with wireless communication.

As described herein, device 200 may perform certain operations inresponse to processing unit 220 executing software instructionscontained in a computer-readable medium, such as memory 230. Acomputer-readable medium may be defined as a non-transitory memorydevice. A memory device may include space within a single physicalmemory device or spread across multiple physical memory devices. Thesoftware instructions may be read into memory 230 from anothercomputer-readable medium or from another device via communicationinterface 260. The software instructions contained in memory 230 maycause processing unit 220 to perform processes described herein.Alternatively, or additionally, hardwired circuitry may be used in placeof or in combination with software instructions to implement processesdescribed herein. Thus, implementations described herein are not limitedto any specific combination of hardware circuitry and software.

Although FIG. 2 shows example components of device 200, in otherimplementations, device 200 may include fewer components, differentcomponents, differently arranged components, or additional componentsthan depicted in FIG. 2. Alternatively, or additionally, one or morecomponents of device 200 may perform one or more tasks described asbeing performed by one or more other components of device 200.

FIG. 3 is a diagram of example operations relating to application scoreserver 150. As illustrated in FIG. 3, application score server 150 maygenerate or obtain security scores for mobile applications hosted bymobile application servers 140. Each security score may include a valuethat relates to the security of a mobile application. In oneimplementation, security scores may be generated as a real value withina predefined range in which higher values represent a more secure mobileapplication. For example, each security score may be a value betweenzero and three, where zero is the lowest (least secure) score possibleand three is the highest (most secure) score possible. The securityscores may be generated or obtained using a number of possibletechniques. For example, each security score may correspond to a scoregenerated based on user ratings for a mobile application or based onother data relating to the mobile application. In general techniques forranking documents or applications are known in the art and can beapplied to obtain the security scores for the mobile applications.

The security scores calculated may be stored by application score server150. The security scores may later be transmitted to other devices, suchas to sentinel applications 130 on mobile devices 120.

As shown in FIG. 3, security scores, generated by application scoreserver 150, are illustrated as security scores 330, which may be storedin a data structure, such as a table. Security scores 330 may relatemobile applications (APP1, APP2, . . . ) to corresponding securityscores (SCORE1, SCORE2, . . . ).

As discussed above, security scores 330 may be determined by applicationscore server 150. Security scores 330 may be additionally augmented ormodified based on the result of a more in-depth analysis of a mobileapplication. In one implementation, the more in-depth analysis may atleast partially include an analysis that includes a manual component,such as an analysis done under the supervision of a technician. Thein-depth analysis may be an optional analysis in which the developer ofa mobile application may opt-in to the analysis. In one implementation,the in-depth analysis may allow for a higher security score for a mobileapplication. For example, a mobile application may be limited, based ononly the analysis performed by the application score server 150, to amaximum security score of three. If the developer of the mobileapplication chooses to have the additional analysis performed, themaximum potential security score for mobile application may be increased(e.g., up to five).

FIG. 4 is a diagram of example operations relating to the modificationof security scores, for mobile applications, based on an in-depthanalysis of a mobile application. As previously discussed, securityscores 330 may include security scores, for mobile applications, thatwere automatically generated, by application score server 150, based onpublically available data relating to the mobile applications.Developers of the mobile applications may be given the option ofinitiating an additional security review process (DEVELOPER INITIATEDREVIEW 410) that provides a more in-depth review of the mobileapplication by a reviewer 420.

Reviewer 420 may represent one or more computer scientists, securityspecialists, or other human operators trained to review mobileapplications based on security risks. Reviewer 420 may evaluate a mobileapplication based on a combination of manual inspection and/or theapplication of automated security assessment tools. Security assessmenttools for computer programs are known and will not be described indetail herein. Reviewer 420 may manually check a number of features ofthe source code of a mobile application and review the results of anumber of automated security assessment tools applied to the mobileapplication. Based on the results of the automated security assessmenttools, reviewer 420 may take further actions relating to the in-depthsecurity assessment.

In one implementation, the developer may be given the choice of a numberof possible levels of an in-depth review. For example, a first level ofin-depth review (referred to as IN-DEPTH SECURITY REVIEW_(—)1 in FIG. 5,below) may include analysis of the binary version of the mobileapplication using one or more automated assessment tools. The analysismay be automatically performed or may be performed or controlled byreviewer 420. A second level of in-depth review (referred to as IN-DEPTHSECURITY REVIEW_(—)2 in FIG. 5) may additionally include analysis of thesource code of the mobile application, by reviewer 420, using one ormore automated and/or manual code assessment tools. The second level ofin-depth review may generally require more time and/or expertise byreviewer 420. The second level of in-depth review may generally bedesigned to identify potential security risks through hands-onfunctional testing, deep inspection of the permissions assigned and usedby the mobile application, input validation, authentication andauthorization performed by the mobile application, and/or error handlingperformed by the mobile application.

In one implementation, the in-depth security review may be conductedbased on a number of security categories, such as the four categories:authenticity, reliability, safety (including vulnerability and malice),and privacy. Security scores may be generated for each of the categoriesand the scores may be combined (e.g., by averaging or summing thecategory security scores to obtain a score corresponding to the in-depthsecurity review).

As a result of the in-depth security review, security scores 330, forselected ones of the mobile applications, may be modified to obtainmodified security scores 430. In one implementation, the in-depthsecurity review may enable the security score, for a particular mobileapplication, to be increased by up to a certain value. For example, amaximum security score based solely on the automated analysis, byapplication score server 150, may be three, and the maximum securityscore based on a combination of the automated and in-depth analysis ofsource code of the mobile application may be five. FIG. 5 is a diagramillustrating an example of a security review process to obtain asecurity score for a mobile application.

In FIG. 5, assume that a developer has developed a mobile application510. The developer may publish mobile application 510 to one or moremobile application servers 140. Application score server 150 mayautomatically generate a security score for mobile application 510(AUTOMATED ANALYSIS 520). The automated analysis may be performedwithout input from the developer and/or without waiting for a specificdecision from the developer.

Application score server 150 may occasionally adjust the automaticallygenerated security score, such as in response to user reviews of mobileapplication 510, developer updates to mobile application, or in responseto other changes in application data 310/320 that relate to mobileapplication 510. As illustrated, in this example, the automaticallyassigned security score may be 2.2 (from a possible range of zero tothree).

The developer may choose to submit mobile application 510 for a morein-depth security review. In this example, assume that two levels ofin-depth security review are offered by the entity that maintainsapplication score server 150. The developer may initially choose a firstlevel of in-depth review. The developer may, for example, fill out aform, including information about the developer, and may submit thebinary version of mobile application 510 for review. A reviewer 420 mayoversee a security review of mobile application 510 using one or moreautomated code assessment tools (IN-DEPTH SECURITY REVIEW_(—)1 530).Alternatively, the in-depth review may be a completely automatedanalysis of the binary version of mobile application 510.

As a result of the first in-depth security review, assume that thesecurity score for mobile application 510 is increased to 3.2 (out of amaximum of 4.0). The developer may choose to submit mobile application510 to another, more rigorous, in-depth security review (IN-DEPTHSECURITY REVIEW_(—)2 540). Although IN-DEPTH SECURITY REVIEW_(—)1 530and IN-DEPTH SECURITY REVIEW_(—)2 are illustrated, in FIG. 5, as beingperformed sequentially, the in-depth security reviews may be independentfrom one another. For instance, a developer may choose only to initiatea first-level in-depth security review, to initiate only a second-levelin-depth security review, or both in-depth security reviews. In someimplementations, a developer of a private mobile application may skipthe automated analysis and elect to have the first or second in-depthsecurity review performed.

The developer may, for example, fill out a form, including informationabout the developer, and submit the binary version of mobile application510 as well as the source code version of mobile application 510, forreview. Reviewer 420 may oversee a security review of mobile application510 using one or more automated and/or manual code assessment tools. Theassessment of mobile application 510 may include an analysis of thesource code. In some implementations, as part of the review process, thedeveloper may be provided with feedback (SECURITY FEEDBACK 550), and inresponse may modify mobile application 510 to increase the security ofmobile application 510. As a result of the second in-depth securityreview, assume that the security score for mobile application 510 isincreased to 4.5 (out of a maximum of 5.0).

The security scores generated by application score server 150 may beused in a number of ways. For example, application score server 150 mayprovide a web interface through which users can view security scores ofmobile applications. As another example, the security scores may beprovided to users that are about to install mobile application as partof a final confirmation before installation. As another example,sentinel application 130 may provide the security scores, of installedmobile applications, to a user of mobile device 120. As yet anotherexample, sentinel application 130 may use the security scores to enforcepolicies at mobile device 120.

FIG. 6 is a flow chart illustrating an example process 600 relating tosentinel application 130. Process 600 may be performed, for example, bysentinel application 130, when sentinel application 130 is initiallystarted, when requested by a user, or on a predefined recurringschedule.

Process 600 may include obtaining a list of mobile applications that areinstalled on mobile device 120 (block 610). Sentinel application 130may, for example, obtain the list of installed applications from theoperating system of mobile device 120. Alternatively or additionally,sentinel application 130 may obtain the list using other techniques. Forinstance, a user may manually identify the mobile applications in whichthe user is interested.

Process 600 may further include obtaining the security score for eachmobile application in the list (block 620). For instance, sentinelapplication 130 may query application score server 150 to obtain asecurity score for each mobile application.

Process 600 may further include providing the security scores to theuser (block 630). In one implementation, the security scores may bepresented in a table that provides the name of each mobile applicationand the corresponding security score. In some implementations, thesecurity scores may be color coded or otherwise visually distinguishedso that low security scores are highlighted. For example, securityscores below a first threshold may be shown using a red font andsecurity scores above a second threshold may be shown using a greenfont.

Through the operation of sentinel application 130, a user can quicklyassess the security risk of the various applications that are installedon mobile device 120. The user may then choose to take remedial action,such as by uninstalling certain mobile applications.

FIG. 7 is a diagram illustrating an example user interface 700 that maybe presented by sentinel application 130. Interface 700 may bepresented, for example, in response to a user opening sentinelapplication 130 or in response to a user selecting a command withinsentinel application 130. As illustrated, interface 700 may provide alist of mobile applications 710 that are installed on mobile device 120.List of mobile applications 710 may include all of the mobileapplications installed on mobile device 120 or a subset of the mobileapplications installed on mobile device 120. For each mobile applicationthat is provided in list of mobile applications 710, a security score720 corresponding to the mobile application may also be provided to theuser.

In the description with respect to FIGS. 6 and 7, the security scoreswere used by sentinel application 130 as a way to inform the user ofmobile device 120 of the potential security risks associated with mobileapplications. Alternatively or additionally, and as will be describedwith respect to FIGS. 6 and 7, sentinel application 130 may interactwith application policy server 160 to provide support for policies thatare based on the security scores.

FIG. 8 is a flow chart illustrating an example process 800 relating toanother implementation of sentinel application 130. Process 800 may beperformed, for example, by a combination of application policy server160 and mobile device 120. With respect to the operations of mobiledevices 120, process 800 may be performed by sentinel applications 130.

Process 800 may include determining policies for mobile devices (block810). The policies may generally relate to mobile applications that arepermitted to be installed and run on mobile devices 120 (block 810). Forexample, a corporation or other entity may manage a number of mobiledevices 120, such as mobile devices provided to employees of thecorporation. It may be desirable that different employees of thecorporation be associated with different security constraints. In thiscase, the corporate policies may indicate that a first group ofemployees may install and/or use mobile applications only if the mobileapplications have at least a first security score. A second group ofemployees may install and/or use mobile applications when the mobileapplications have at least a second security score. In otherimplementations, other rules may be enforced by the policies. Forexample, the policy may indicate that any mobile application that useslocation tracking may not be installed and/or used.

Process 800 may further include transmitting the policies to therelevant mobile devices (block 820). Application policy server 160 may,for example, transmit a message to sentinel application 130 of eachmobile device 120 that is the subject of a policy. The message mayinclude the particular policy for mobile device 120. Sentinelapplication 130 may receive the message and may implement the policiesincluded in the message.

Process 800 may further include obtaining the security score for eachinstalled mobile application (block 830). For instance, sentinelapplication 130 may query application score server 150 to obtain asecurity score for each mobile application that is installed on themobile device.

Process 800 may further include implementing the policies by blockinginstallation, uninstalling and/or disabling, or requesting that the useruninstall and/or disable installed mobile applications that violate thepolicies (block 840). In one implementation, sentinel application 130may block the installation of mobile applications that do not meet thepolicies installed on mobile device 120. Alternatively or additionally,sentinel application 130 may block the execution of mobile applicationsthat do not meet the policies installed on mobile device 120.Alternatively or additionally, sentinel application 130 may notify theuser or notify an administrator, at application policy server 160, whenan application is executed that does not meet the policies installed onmobile device 120. In general, the policies may be implemented using thesecurity scores that were obtained from application score server 150.

FIG. 9 is a diagram illustrating an example of the operation ofapplication policy server 160. As shown, in this example, applicationpolicy server 160 may provide policies to two mobile devices, the firstof which may execute sentinel application 710 (SENTINELAPPLICATION_(—)1) and the second of which may execute sentinelapplication 720 (SENTINEL APPLICATION_(—)2). Application policy server160 may transmit a policy, POLICY_(—)1, to sentinel application 710 andmay transmit another policy, POLICY_(—)2, sentinel application 720.Sentinel applications 710 and 720 may operate based on the respectivepolicies to potentially implement different rules or constraints. Forexample, sentinel application 710 may only allow certain categories ofmobile applications to be executed at the mobile device associated withsentinel application 710. As another example, sentinel application 720may only allow mobile applications having a security score greater thana threshold value to be executed at the mobile device associated withsentinel application 720.

As described above, mobile applications may be automatically evaluatedand given scores based on the security risks associated with the mobileapplications. Different levels of security assessment may be availableto a developer of a mobile application. For example, a developer maychoose to submit a mobile application for a more in-depth securityassessment of the mobile application. An application or service thatexecutes at a mobile device may enable users of the mobile device orentities that have control or responsibility of the mobile device toeasily make security and risk based policy decisions relating to thesecurity risks that are acceptable to the owners of the mobile device.

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit theimplementations to the precise form disclosed. Modifications andvariation are possible in light of the above teachings or may beacquired from practice of the invention.

For example, while series of blocks have been described with regard toFIGS. 6 and 8, the order of the blocks may be modified in otherimplementations. Further, non-dependent blocks may be performed inparallel.

It will be apparent that example aspects, as described above, may beimplemented in many different forms of software, firmware, and hardwarein the implementations illustrated in the figures. The actual softwarecode or specialized control hardware used to implement these aspectsshould not be construed as limiting. Thus, the operation and behavior ofthe aspects were described without reference to the specific softwarecode, it being understood that software and control hardware could bedesigned to implement the aspects based on the description herein.

Further, certain portions of the invention may be implemented as “logic”that performs one or more functions. This logic may include hardware,such as an ASIC or a FPGA, or a combination of hardware and software.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the invention. In fact, many of these features may becombined in ways not specifically recited in the claims and/or disclosedin the specification. Although each dependent claim listed below maydirectly depend on only one other claim, the disclosure of the inventionincludes each dependent claim in combination with every other claim inthe claim set.

No element, act, or instruction used in the present application shouldbe construed as critical or essential unless explicitly described assuch. Also, as used herein, the article “a” is intended to include oneor more items. Where only one item is intended, the term “one” orsimilar language is used. Further, the phrase “based on” is intended tomean “based, at least in part, on” unless explicitly stated otherwise.

1-10. (canceled)
 11. A method comprising: requesting, by a mobiledevice, one or more security scores of one or more mobile applications,the one or more security scores defining a level of security riskcorresponding to the one or more mobile applications; receiving, by themobile device, a policy relating to mobile applications that arepermitted to be used by the mobile device, the policy including athreshold security score value; receiving, by the mobile device, therequested one or more security scores; and restricting, by the mobiledevice, use of a selected mobile application, of the one or more mobileapplications, when a security score, of the one or more receivedsecurity scores, corresponding to the selected mobile application isbelow the threshold security score value.
 12. The method of claim 11,where the restricting the use of the selected mobile application furtherincludes: preventing the selected mobile application from beinginstalled on the mobile device; preventing the selected mobileapplication from being executed by the mobile device; providing a userof the mobile device with a notification when the selected mobileapplication is executed by the mobile device; or uninstalling theselected mobile application from the mobile device.
 13. The method ofclaim 11, further comprising: providing a graphical indication of aplurality of mobile applications that are installed on the mobile deviceand corresponding security scores of the installed plurality of mobileapplications.
 14. The method of claim 11, where the requested one ormore security scores correspond to security scores of mobileapplications installed at the mobile device.
 15. The method of claim 11,where the requested one or more security scores include security scoresdetermined, at least in part, through a manual analysis of the mobileapplications.
 16. A device comprising: a processor to: request one ormore security scores for one or more mobile applications, the one ormore security scores defining a level of security risk corresponding tothe one or more mobile applications; receive a policy relating to mobileapplications that are permitted to be used by the device, the policyincluding a threshold security score value; receive the requested one ormore security scores; and restrict use of a selected mobile application,of the one or more mobile applications, when a security score, of theone or more received security scores, corresponding to the selectedmobile application is below the threshold security score value.
 17. Thedevice of claim 16, where, when restricting the use of the selectedmobile application, the processor is further to: prevent the selectedmobile application from being installed on the device; prevent theselected mobile application from being executed by the device; provide auser of the device with a notification when the selected mobileapplication is executed by the device; or uninstall the selected mobileapplication from the device.
 18. The device of claim 16, where theprocessor is further to: provide a graphical indication of all aplurality of mobile applications that are installed on the device andcorresponding security scores of the installed plurality of mobileapplications.
 19. The device of claim 16, where the requested one ormore security scores correspond to security scores of mobileapplications installed at the device.
 20. The device of claim 16, wherethe requested one or more security scores include security scoresdetermined, at least in part, through a manual analysis of the mobileapplications.
 21. The method of claim 11, further comprising: providing,for presentation, the requested one or more security scores.
 22. Themethod of claim 11, where when requesting the one or more securityscores, the method includes: requesting a first security score, of theone or more security scores, for a first mobile application of the oneor more mobile applications; and requesting a second security score, ofthe one or more security scores, for a second mobile application of theone or more mobile applications, when receiving the requested one ormore security scores, the method includes: receiving the first securityscore, and receiving the second security score, and the method furtherincludes: providing, for presentation, the received first security scoreand the received second security score.
 23. The device of claim 16,where the processor is further to: provide, for presentation, therequested one or more security scores.
 24. The device of claim 16, wherethe processor, when requesting the one or more security scores, isfurther to: request a first security score, of the one or more securityscores, for a first mobile application of the one or more mobileapplications; and request a second security score, of the one or moresecurity scores, for a second mobile application of the one or moremobile applications, the processor, when receiving the requested one ormore security scores, is further to: receive the first security score,and receive the second security score, and the processor is further to:provide, for presentation, the received first security score and thereceived second security score.
 25. A non-transitory computer readablemedium storing instructions, the instructions comprising: one or moreinstructions which, when executed by a processor of a device, cause theprocessor to: request one or more security scores for one or moreapplications, the one or more security scores defining a level ofsecurity risk corresponding to the one or more applications; receive apolicy relating to applications that are permitted to be used by thedevice, the policy including a threshold security score value; receivethe requested one or more security scores; and restrict use of aselected application, of the one or more applications, when a securityscore, of the one or more received security scores, corresponding to theselected application is below the threshold security score value. 26.The non-transitory computer readable medium of claim 25, where the oneor more instructions to restrict the use of the selected applicationinclude: one or more instructions to prevent the selected applicationfrom being installed on the device; one or more instructions to preventthe selected application from being executed by the device; one or moreinstructions to provide a user of the device with a notification whenthe selected application is executed by the device; or one or moreinstructions to uninstalling the selected application from the device.27. The non-transitory computer readable medium of claim 25, where theinstructions further comprise: one or more instructions to provide agraphical indication of a plurality of applications that are installedon the device and corresponding security scores of the installedplurality of applications.
 28. The non-transitory computer readablemedium of claim 25, where the requested one or more security scorescorrespond to security scores of applications installed at the device,and the requested one or more security scores include security scoresdetermined, at least in part, through a manual analysis of theapplications.
 29. The non-transitory computer readable medium of claim25, where the instructions further comprise: one or more instructions toprovide, for presentation, the requested one or more security scores.30. The non-transitory computer readable medium of claim 25, where theone or more instructions to request the one or more security scoresfurther include: one or more instructions to request a first securityscore, of the one or more security scores, for a first application ofthe one or more applications; and one or more instructions to request asecond security score, of the one or more security scores, for a secondapplication of the one or more applications, the one or moreinstructions to receive the requested one or more security scoresfurther include: one or more instructions to receive the first securityscore, and one or more instructions to receive the second securityscore, and the instructions further include: one or more instructions toprovide, for presentation, the received first security score and thereceived second security score.